Managed Messaging Platform

ABSTRACT

Software is executed on a wireless device for presenting a response aggregation drawn upon a message having at least two desired recipients. The software of presenting at least two message-structure item questions via the wireless device and receives input requesting response aggregation drawn upon the message having at least two desired recipients and transmits the message to at least one of the at least two desired recipients using the wireless device.

CROSS-REFERENCES TO RELATED APPLICATIONS

This patent application is a continuation of patent application Ser. No.09/894,278, filed Jun. 27, 2001, which claims the benefit under 35U.S.C. 119(e) of Provisional Patent Application No. 60/282,381, filedApr. 5, 2001, both of which are incorporated herein by reference intheir entirety.

FIELD OF THE INVENTION

The present application relates, in general, to wireless communication.

BACKGROUND

Wireless communication refers to communication between sending andreceiving stations via electromagnetic radiation not guided by any hardphysical path (e.g., by microwave link). Examples of wirelesscommunication are communication via cellular telephony systems, PersonalCommunication Systems, or Global System for Mobile Communicationsystems.

Wireless communication is typically accomplished via users exchangingvoice and/or alphanumeric data via use of at least one wireless device.One example of wireless communication is that of a first wireless-deviceuser exchanging voice and/or alphanumeric data with a group of two ormore other wireless-device users.

It has been noted by the inventors named herein (the inventors) thatwhen a first wireless-device user finds it advantageous to exchangevoice and/or alphanumeric data with a group of wireless-device users,the first wireless-device user either may want to disseminateinformation to the group, or may instead want to both disseminateinformation to the group and receive feedback from the group members inresponse to the disseminated information. It has been further noted bythe inventors that when such group communication is performed in therelated art, it is generally done manually, in that the firstwireless-device user must generally contact each of the group membersand disseminate the voice and/or alphanumeric data on an individualbasis. Thereafter, typically the first wireless-device user manuallyaggregates and transforms the responses from the users in the group ifsuch aggregation or transformation is desired.

The inventors have noted that there are several disadvantages to themanual method of the related art. First, the inventors have noted thatit is very tedious and time intensive to contact and disseminateinformation to the group, particularly if data transmission is involved.Second, the inventors have noted that insofar as group members may betemporarily unavailable, the first wireless-device user must seek torepetitively call the unavailable group members. Third, the inventorshave noted that it is very tedious and time intensive to manuallyaggregate and transform responses from the group members. Fourth, theinventors have noted that if a group member is not interested in eitherreceiving or responding to the disseminated information, the firstwireless-device user essentially wastes his time by contacting thedisinterested user. Fifth, the inventors have noted that if a groupmember is undecided in his response to the disseminated information, thefirst wireless-device user must repetitively contact such undecidedgroup member to see if the undecided group member has yet arrived at adecision. In addition to the foregoing, other disadvantages exist whichwill be appreciated by those having ordinary skill in the art.

In light of the foregoing, the inventors have noted that a need existsin the art for a method and system that will allow a wireless deviceuser to easily disseminate information to and collect information from agroup of wireless-device users.

SUMMARY OF THE INVENTION

The inventors have devised a method and system that will allow awireless device user to easily disseminate information to and collectinformation from a group of wireless-device users.

In one embodiment, a method includes but is not limited to presenting,via a wireless device, a response aggregation drawn upon a messagehaving at least two desired recipients.

In another embodiment, a method includes but is not limited toaccepting, via a wireless device, user input requesting responseaggregation drawn upon a message having at least two desired recipients.

In another embodiment, a method includes but is not limited topresenting at least two message-structure item questions via a wirelessdevice.

In another embodiment, a method includes but is not limited to receivinginput requesting response aggregation drawn upon a message having atleast two desired recipients; and transmitting the message to at leastone of the at least two desired recipients, wherein said transmitting isvia at least one wireless device.

In another embodiment, a method includes but is not limited totransmitting, via a wireless device, a message having at least twodesired recipients.

In addition to the foregoing, other method embodiments are described inthe claims, drawing, and text forming a part of the present application.

In one or more various embodiments, related systems include but are notlimited to circuitry for effecting the foregoing-described methodembodiments; the circuitry can be virtually any combination of hardware,software, and/or firmware configured to effect the foregoing-describedmethod embodiments depending upon the design choices of the systemdesigner.

The foregoing is a summary and thus contains, by necessity;simplifications, generalizations and omissions of detail; consequently,those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and/orprocesses described herein, as defined solely by the claims, will becomeapparent in the non-limiting detailed description set forth herein.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of thisinvention will become more readily appreciated as the same become betterunderstood by reference to the following detailed description, whentaken in conjunction with the accompanying drawings, wherein:

FIG. 1 shows a pictographic representation of an environment whereinmethods and systems described herein may be utilized.

FIG. 2 depicts a process via a wireless device, a response toaggregation drawn upon a message having at least two desired recipients.

FIG. 3 depicts that, in one implementation, method step 202 includesmethod step 300.

FIG. 8B depicts an example of a scheme used by many implementationsherein when presenting a desired-recipient response summary having atleast one display of aggregate message-related activities of the atleast two desired recipients as described in method step 300.

FIG. 4 depicts that, in one implementation, of method step 300,presenting a desired-recipient response summary having at least onedisplay of aggregate message-related activities of the at least twodesired recipients can include, but is not limited to, method steps 400and 402.

FIG. 5 depicts that, in one implementation, of method step 300,presenting a desired-recipient response summary having at least onedisplay of aggregate message-related activities of the at least twodesired recipients can include, but is not limited to, method steps 500and 502.

FIG. 6 shows in one implementation, of method step 300, presenting adesired-recipient response summary having at least one display ofaggregate message-related activities of the at least two desiredrecipients can include, but in not limited to, method steps 600 and 602.

FIG. 7 depicts that, in one implementation, of method step 300,presenting a desired-recipient response summary having at least onedisplay of aggregate message-related activities of the at least twodesired recipients can include, but is not limited to, method steps 700and 702.

FIG. 8A depicts that, in one implementation, of method step 300,presenting a desired-recipient response summary having at least onedisplay of aggregate message-related activities of the at least twodesired recipients can include, but is not limited to, method steps 800and 802

FIG. 9 depicts that, in one implementation, of method step 300,presenting a desired-recipient response summary having at least onedisplay of aggregate message-related activities of the at least twodesired recipients can include, but is not limited to, method steps 900and 902.

FIG. 10 shows a process via a wireless device, user input requestingresponse aggregation drawn upon a message having at least two desiredrecipients.

FIG. 11A shows that, in one implementation, method step 1002 includesmethod step 1100.

FIG. 11B-E depicts an example of a scheme used by many implementationsherein when accepting user input defining the at least two desiredrecipients via entry of at least one desired-recipient item as describedin method step 1100.

FIG. 12 shows that, in one implementation, method step 1100 includesmethod step 1200.

FIG. 13 shows that, in one implementation, method step 1002 includesmethod step 1300.

FIG. 14 depicts that, in one implementation, method step 1300 includesmethod step 1400.

FIG. 15 shows that, in one implementation, method step 1002 includesmethod step 1500.

FIG. 16 depicts a process that illustrates presenting at least twoquestions via a wireless device.

FIG. 17 shows that, in one implementation, method step 1602 includesmethod step 1700.

FIG. 18A depicts in one implementation, method step 1602 includes methodstep 1800.

FIGS. 18B-C depicts an example of a scheme used in one implementation ofdisplaying a message having at least one message-structure item.

FIG. 19 shows that, in one implementation, method step 1800 includesmethod step 1900.

FIG. 20 shows a process that illustrates the receiving input requestingresponse aggregation drawn upon a message having at least two desiredrecipients.

FIG. 21 shows that, in one implementation, method step 2004 includesmethod step 2100.

FIG. 22 shows that, in one implementation, method step 2004 includesmethod step 2200.

FIG. 23 shows that, in one implementation, method step 2004 can include,but is not limited to, method steps 2300-2306.

FIG. 24 shows that, in one implementation, method step 2300 can includemethod step 2400.

FIG. 25 shows that, in one implementation, method step 2400 can includemethod step 2500.

FIG. 34 shows an implementation of the high-level logic flowchart shownin FIG. 25.

FIG. 35 shows two alternate implementations of the high-level logicflowchart shown in FIG. 34.

FIG. 26 shows that, in one implementation, method step 2400 can includemethod step 2600.

FIG. 27 shows that, in one implementation, method step 2302 can includemethod step 2700.

FIG. 28 shows that, in one implementation, method step 2304 can includemethod step 2800.

FIG. 29 depicts that, in one implementation, method step 2004 includesmethod step 2900.

FIG. 30 shows that, in one implementation, method step 2004 includesmethod step 3000.

FIG. 31 shows that, in one implementation, method step 2002 includesmethod step 3100.

FIG. 32 shows that, in one implementation, method step 2002 includesmethod step 3200.

FIG. 33 depicts a pictorial representation of a conventional dataprocessing system in which illustrative embodiments of the devicesand/or processes described herein may be implemented.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

With reference now to FIG. 1, shown is a pictographic representation ofan environment wherein methods and systems described herein may beutilized. First, depicted in FIG. 1 is that sender 100, by use ofwireless device 102 creates a message via communication with ManagedMessaging Platform (MMP) engine 104 (as shown, wireless device 102 maybe any type of wireless device such as a Wireless Application Protocol(WAP) phone, a wireless Personal Digital Assistant (PDA), or a two-waypager). Second, illustrated is that MMP engine 104 sends messagenotifications to each wireless device 108 associated with each desiredrecipient forming group of desired recipients 106 (as shown, eachwireless device 108 may be any type of wireless device such as aWireless Application Protocol (WAP) phone, a wireless Personal DigitalAssistant (PDA), or a two-way pager). Third, shown is that one or moredesired recipients in group of desired recipients 106 view and/orrespond to the message via communication with MMP engine 104, where suchviewing and/or responding is achieved via each desired recipient's useof his or her respective wireless device 108. Fourth, depicted is thatsender 100, via communication with MMP engine 104, uses his wirelessdevice 102 to check the message status and responses, where the statusesand responses may have been aggregated by MMP engine 104. For moredetails related to the foregoing scheme, please see herein incorporatedby reference Provisional Patent Application 60/282,381.

Following are a series of flowcharts depicting implementations ofprocesses. For ease of understanding, the flowcharts are organized suchthat the initial flowcharts present implementations via an overall “bigpicture” viewpoint and thereafter the following flowcharts presentalternate implementations and/or expansions of the “big picture”flowcharts as either substeps or additional steps building on one ormore earlier-presented flowcharts. Those having ordinary skill in theart will appreciate that the style of presentation utilized herein(e.g., beginning with a presentation of a flowchart(s) presenting anoverall view and thereafter providing additions to and/or furtherdetails in subsequent flowcharts) generally allows for a rapid and easyunderstanding of the various process implementations.

I. Managed Messaging as Observed from a Sender's Wireless Device

A. Displaying Response Aggregation Via a Sender's Wireless Device

Referring now to FIG. 2, shown is a high-level logic flowchart depictinga process. Method step 200 depicts the start of process. Method step 202illustrates presenting, via a wireless device (e.g., wireless device102), a response aggregation drawn upon a message having at least twodesired recipients (e.g., group of desired recipients 106). Method step204 shows the end of the process.

With reference now to FIG. 3, shown is an implementation of thehigh-level logic flowchart shown in FIG. 2. Depicted in FIG. 3 is that,in one implementation, method step 202 includes method step 300. Methodstep 300 shows that, in one implementation, presenting, via a wirelessdevice, a response aggregation drawn upon a message having at least twodesired recipients can include, but is not limited to, presenting adesired-recipient response summary having at least one display ofaggregate message-related activities of the at least two desiredrecipients. (For example, such as was at least partially described inthe herein incorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 3 function substantiallyas described elsewhere herein.

Referring now to FIG. 8B, depicted is an example of a scheme used bymany implementations herein when presenting a desired-recipient responsesummary having at least one display of aggregate message-relatedactivities of the at least two desired recipients as described in methodstep 300. Specifically, shown is a pictographic representation of awireless device screen having an implementation of desired-recipientresponse summary 850 which shows a total number of 6 desired recipientsin a group of desired recipients to whom a message has been sent, andthat of those 6 desired recipients, 5 have viewed the message (of which4 have indicated that they will not be attending a meeting or event towhich the message is related, while 1 has indicated he or she will beattending a meeting or event to which the message is related), 1 has notviewed the message, 0 of the desired recipients are unreachable (i.e., 0messages were detected undeliverable).

Referring now again to FIG. 8B shown is that, in one implementation, itis possible to “drill down” into the “not attending” aspect ofdesired-recipient response summary 850, which results in the display ofa list of addresses of those desired recipients who have responded tothe message that they are NOT attending. In addition, further depictedis that it is possible to further “drill down” into individually listeddesired recipients to gain more information related to such desiredrecipients (e.g., name, email address, time the message was sent to thedesired recipient, the time the message was viewed by the desiredrecipient, an RSVP by the desired recipient, and a comment from thedesired recipient).

With reference now to FIG. 4, shown is an implementation of thehigh-level logic flowchart shown in FIG. 3. Depicted in FIG. 4 is that,in one implementation, of method step 300, presenting adesired-recipient response summary having at least one display ofaggregate message-related activities of the at least two desiredrecipients can include, but is not limited to, method steps 400 and 402.Method step 400 shows displaying a number of desired recipients who haveviewed the message. Method step 402 depicts displaying, for at least onedesired recipient who has viewed the message, at least onedesired-recipient item selected from a desired-recipient-item groupincluding the at least one desired recipient's name, the at least onedesired recipient's email address, the message's title, a date themessage was sent, a date the at least one desired recipient viewed themessage, and a comment by the at least one desired recipient; typically(but not always) method step 402 occurs in response to user input. (Forexample, such as was at least partially described in the hereinincorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 4 function substantiallyas described elsewhere herein.

In one implementation, method steps 400 and 402 are effected via adrill-down scheme analogous to that depicted and described in relationto FIG. 8B.

With reference now to FIG. 5, shown is an implementation of thehigh-level logic flowchart shown in FIG. 3. Depicted in FIG. 5 is that,in one implementation, of method step 300, presenting adesired-recipient response summary having at least one display ofaggregate message-related activities of the at least two desiredrecipients can include, but is not limited to method steps 500 and 502.Method step 500 shows displaying a number of desired recipients who haveNOT viewed the message. Method step 502 depicts displaying, for at leastone desired recipient who has NOT viewed the message, at least onedesired-recipient item selected from a desired-recipient-item groupincluding the message's title, a date the message was sent, the at leastone desired recipient's name, and the at least one desired recipient'semail address; typically method step 502 occurs in response to userinput. (For example, such as was at least partially described in theherein incorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 5 function substantiallyas described elsewhere herein. In one implementation, method steps 500and 502 are effected via a drill-down scheme analogous to that depictedand described in relation to FIG. 8B.

With reference now to FIG. 6, shown is an implementation of thehigh-level logic flowchart shown in FIG. 3. Depicted in FIG. 6 is that,in one implementation, of method step 300, presenting adesired-recipient response summary having at least one display ofaggregate message-related activities of the at least two desiredrecipients can include, but is not limited to, method steps 600 and 602.Method step 600 shows displaying a number of desired recipients for whomthe message was undeliverable. Method step 602 depicts displaying, forat least one desired recipient for whom the message was undeliverable,the message's title, a date the message was sent, at least onedesired-recipient item selected from a desired-recipient-item groupincluding the at least one desired recipient's name, and the at leastone desired recipient's email address. (For example, such as was atleast partially described in the herein incorporated by referenceProvisional Patent Application No. 60/282,381.) The remaining methodsteps of FIG. 6 function substantially as described elsewhere herein. Inone implementation, method steps 600 and 602 are effected via adrill-down scheme analogous to that depicted and described in relationto FIG. 8B.

With reference now to FIG. 7, shown is an implementation of thehigh-level logic flowchart shown in FIG. 3. Depicted in FIG. 7 is that,in one implementation, of method step 300, presenting adesired-recipient response summary having at least one display ofaggregate message-related activities of the at least two desiredrecipients can include, but is not limited to, method steps 700 and 702.Method step 700 shows displaying a number of desired recipientsattending a meeting or an event. Method step 702 depicts displaying, forat least one desired recipient who is attending the meeting or theevent, at least one desired-recipient item selected from adesired-recipient-item group including the at least one desiredrecipient's name, the at least one desired recipient's email address,the message's title, a date the message was sent, a date the at leastone desired recipient viewed the message, and a comment by the at leastone desired recipient. (For example, such as was at least partiallydescribed in the herein incorporated by reference Provisional PatentApplication No. 60/282,381.) The remaining method steps of FIG. 7function substantially as described elsewhere herein. In oneimplementation, method steps 700 and 702 are effected via a drill-downscheme analogous to that depicted and described in relation to FIG. 8B.

With reference now to FIG. 8A, shown is an implementation of thehigh-level logic flowchart shown in FIG. 3. Depicted in FIG. 8A is that,in one implementation, of method step 300, presenting adesired-recipient response summary having at least one display ofaggregate message-related activities of the at least two desiredrecipients can include, but is not limited to, method steps 800 and 802.Method step 800 shows displaying a number of desired recipients NOTattending a meeting or an event. Method step 802 depicts displaying, forat least one desired recipient who is NOT attending the meeting or theevent, at least one desired-recipient item selected from adesired-recipient-item group including the at least one desiredrecipient's name, the at least one desired recipient's email address,the message's title, a date the message was sent, a date the at leastone desired recipient viewed the message, and a comment by the at leastone desired recipient. (For example, such as was at least partiallydescribed in the herein incorporated by reference Provisional PatentApplication No. 60/282,381.) The remaining method steps of FIG. 8Afunction substantially as described elsewhere herein. In oneimplementation, method steps 800 and 802 are effected via a drill-downscheme analogous to that depicted and described in relation to FIG. 8B.

Referring now again to FIG. 8B shown is that, in one implementation, itis possible to “drill down” into the “not attending” aspect ofdesired-recipient response summary 850 which results in the display of alist of addresses of those desired recipients who have responded to themessage that they are NOT attending. In addition, further depicted isthat it is possible to further “drill down” into individually listeddesired recipients to gain more information related to such desiredrecipients (e.g., name, email address, time the message was sent to thedesired recipient, the time the message was viewed by the desiredrecipient, an RSVP by the desired recipient, and a comment from thedesired recipient).

With reference now to FIG. 9, shown is an implementation of thehigh-level logic flowchart shown in FIG. 3. Depicted in FIG. 9 is that,in one implementation, of method step 300, presenting adesired-recipient response summary having at least one display ofaggregate message-related activities of the at least two desiredrecipients can include, but is not limited to, method steps 900 and 902.Method step 900 shows displaying a number of desired recipientsundecided as to a meeting or an event. Method step 902 depictsdisplaying, for at least one desired recipient who is undecided as tothe meeting or the event, at least one desired-recipient item selectedfrom a desired-recipient-item group including the message title, a datethe message was sent, the at least one desired recipient's name, and theat least one desired recipient's email address. (For example, such aswas at least partially described in the herein incorporated by referenceProvisional Patent Application No. 60/282,381.) The remaining methodsteps of FIG. 9 function substantially as described elsewhere herein. Inone implementation, method steps 900 and 902 are effected via adrill-down scheme analogous to that depicted and described in relationto FIG. 8B.

B. Specifying Response Aggregation Via Sender's Wireless Device

Referring now to FIG. 10, shown is a high-level logic flowchartdepicting a process. Method step 1000 depicts the start of process.Method step 1002 illustrates accepting, via a wireless device, userinput requesting response aggregation drawn upon a message having atleast two desired recipients. Method step 1004 shows the end of theprocess.

With reference now to FIG. 11A, shown is an implementation of thehigh-level logic flowchart shown in FIG. 10. Depicted in FIG. 11A isthat, in one implementation, method step 1002 includes method step 1100.Method step 1100 shows that, in one implementation, accepting, via awireless device, user input requesting response aggregation drawn upon amessage having at least two desired recipients can include, but is notlimited to, accepting user input defining the at least two desiredrecipients via entry of at least one desired-recipient item. (Forexample, such as was at least partially described in the hereinincorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 11A functionsubstantially as described elsewhere herein.

Referring now to FIG. 11B-E, depicted is an example of a scheme used bymany implementations herein when accepting user input defining the atleast two desired recipients via entry of at least one desired-recipientitem as described in method step 1100. Illustrated in FIGS. 11B-E is aset of user interactions between a user and a wireless device wherebythe user creates and sends a type of message known as a “memo.”

Following are several flowchart-based descriptions of variousimplementations of systems and devices. In general, with respect tointeractions via wireless devices, implementations of theseflowchart-based descriptions follow the example scheme set forth inFIGS. 11B-E. That is, in general implementations follow the approachwhereby a user can define a message via entry of data through a wirelessdevice via a scheme analogous to that shown and described in relation toFIGS. 11B-E.

Reference to Provisional Patent Application No. 60/282,381, entitledWIRELESS PAYMENT PROCESSING, which is hereby incorporated by referencein its entirety, will show that in Provisional Patent Application No.60/282,381 a “structured message” is described as a “memo,” and thatextensions of the “memo” are therein described as a “meeting,” and an“event.” The description herein substantially follows the convention inthe provisional by defining a set of attributes (“message-structureitems”) for messages and thereafter expanding those attributes toencompass meetings and/or events, where appropriate.

With reference now to FIG. 12, shown is an implementation of thehigh-level logic flowchart shown in FIG. 11. Depicted in FIG. 12 isthat, in one implementation, method step 1100 includes method step 1200.Method step 1200 shows that, in one implementation, accepting user inputdefining the at least two desired recipients via entry of at least onedesired-recipient item can include, but is not limited to, acceptinguser input defining the at least two desired recipients via entry of atleast one desired-recipient item wherein the at least one desiredrecipient item is selected from a desired-recipient-item group whichincludes a desired recipient name, a desired recipient address, a choiceof a group name, and a choice of a contact. (For example, such as was atleast partially described in the herein incorporated by referenceProvisional Patent Application No. 60/282,381.) The remaining methodsteps of FIG. 12 function substantially as described elsewhere herein.In one implementation method step 1200 is accomplished via a schemeanalogous to that shown and described in relation to FIGS. 11B-E.

With reference now to FIG. 13, shown is an implementation of thehigh-level logic flowchart shown in FIG. 10. Depicted in FIG. 13 isthat, in one implementation, method step 1002 includes method step 1300.Method step 1300 shows that, in one implementation, accepting, via awireless device, user input requesting response aggregation drawn upon amessage having at least two desired recipients can include, but is notlimited to, accepting user input defining the message to have at leastone message-structure item. (For example, such as was at least partiallydescribed in the herein incorporated by reference Provisional PatentApplication No. 60/282,381.) The remaining method steps of FIG. 13function substantially as described elsewhere herein. In oneimplementation method step 1300 is accomplished via a scheme analogousto that shown and described in relation to FIGS. 11B-E.

With reference now to FIG. 14, shown is an implementation of thehigh-level logic flowchart shown in FIG. 13. Depicted in FIG. 14 isthat, in one implementation, method step 1300 includes method step 1400.Method step 1400 shows that, in one implementation, accepting user inputdefining the message to have at least one message-structure item caninclude, but is not limited to, the at least one message-structure itemselected from a message-structure-item group which includes a subject; aresponse option; an associated ability to allow at least one desiredrecipient to see at least one other of the at least two desiredrecipients; a message body; at least one yes-no-type answer question; atleast one numeric-response-type answer question; at least onetextual-response-type answer question; at least onemultiple-choice-response-type answer question; at least one meeting datewhich can include either or both a day and a time; at least one meetinglocation; at least one meeting RSVP request; at least one eventdescriptor wherein the event descriptor can include, but is not limitedto, a party, a breakfast, a lunch, a dinner, a movie, a game, a concert,or a miscellaneous occurrence; at least one event location; and at leastone event RSVP request. (For example, such as was at least partiallydescribed in the herein incorporated by reference Provisional PatentApplication No. 60/282,381.) The remaining method steps of FIG. 14function substantially as described elsewhere herein. In oneimplementation, method step 1400 is accomplished via a scheme analogousto that shown and described in relation to FIGS. 11B-E.

With reference now to FIG. 15, shown is an implementation of thehigh-level logic flowchart shown in FIG. 10. Depicted in FIG. 15 isthat, in one implementation, method step 1002 includes method step 1500.Method step 1500 shows that, in one implementation, accepting, via awireless device, user input requesting response aggregation drawn upon amessage having at least two desired recipients can include, but is notlimited to, accepting voice, alphanumeric, or digital input. (Forexample, such as was at least partially described in the hereinincorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 15 functionsubstantially as described elsewhere herein. In one implementationmethod step 1500 is accomplished via a scheme analogous to that shownand described in relation to FIGS. 11B-E.

II. Managed Messaging as Observed from Recipient's Wireless Device

Referring now to FIG. 16, shown is a high-level logic flowchartdepicting a process. Method step 1600 depicts the start of process.Method step 1602 illustrates presenting at least two message-structureitem questions via a wireless device. Method step 1604 shows the end ofthe process.

With reference now to FIG. 17, shown is an implementation of thehigh-level logic flowchart shown in FIG. 16. Depicted in FIG. 17 isthat, in one implementation, method step 1602 includes method step 1700.Method step 1700 shows that, in one implementation, presenting at leasttwo message-structure item questions via a wireless device can include,but is not limited to, displaying the at least two message-structureitem questions concurrently or sequentially. (For example, such as wasat least partially described in the herein incorporated by referenceProvisional Patent Application No. 60/282,381.) The remaining methodsteps of FIG. 17 function substantially as described elsewhere herein.

With reference now to FIG. 18A, shown is an implementation of thehigh-level logic flowchart shown in FIG. 16. Depicted in FIG. 18A isthat, in one implementation, method step 1602 includes method step 1800.Method step 1800 shows that, in one implementation, presenting at leasttwo message-structure item questions via a wireless device can include,but is not limited to, displaying a message having at least onemessage-structure item. (For example, such as was at least partiallydescribed in the herein incorporated by reference Provisional PatentApplication No. 60/282,381.) The remaining method steps of FIG. 18Afunction substantially as described elsewhere herein.

Referring now to FIGS. 18B-C, depicted is an example of a scheme used inone implementation of displaying a message having at least onemessage-structure item. Following are flowchart-based descriptions ofvarious implementations of systems and devices. In general, with respectto presentation via wireless devices, implementations of these flowchartbased descriptions follow the example scheme set forth in FIGS. 18B-C.

With reference now to FIG. 19, shown is an implementation of thehigh-level logic flowchart shown in FIG. 18A. Depicted in FIG. 19 isthat, in one implementation, method step 1800 includes method step 1900.Method step 1900 shows that, in one implementation, displaying a messagehaving at least one message-structure item can include, but is notlimited to, the at least one message-structure item selected from amessage-structure-item group which includes a subject; a responseoption; an associated ability to allow at least one desired recipient tosee at least one other of the message's recipients; a message body; atleast one yes-no-type answer question; at least onenumeric-response-type answer question; at least onetextual-response-type answer question; at least onemultiple-choice-response-type answer question; at least one meeting datewhich can include either or both a day and a time; at least one meetinglocation; at least one meeting RSVP request; at least one eventdescriptor wherein the event descriptor can include, but is not limitedto, a party, a breakfast, a lunch, a dinner, a movie, a game, a concert,or a miscellaneous occurrence; at least one event location; and at leastone event RSVP request. (For example, such as was at least partiallydescribed in the herein incorporated by reference Provisional PatentApplication No. 60/282,381.) The remaining method steps of FIG. 19function substantially as described elsewhere herein.

III. Managed Messaging as Observed from Server Entity (e.g., MMP Engine104)

With reference now to FIG. 20, shown is an implementation of ahigh-level logic flowchart depicting a process. Method step 2000 depictsthe start of the process. Method step 2002 illustrates receiving inputrequesting response aggregation drawn upon a message having at least twodesired recipients (e.g., MMP engine 104 receiving one or more packetscontaining such input from wireless device 102). Method step 2004illustrates transmitting the message to at least one of the at least twodesired recipients, wherein said transmitting is via at least onewireless device (e.g., MMP engine 104 transmitting one or more packetscontaining the message to one or more recipients of group 106 via suchone or more recipients' respective wireless devices 108). Method step2006 shows the end of the process.

With reference now to FIG. 21, shown is an implementation of thehigh-level logic flowchart shown in FIG. 20. Depicted in FIG. 21 isthat, in one implementation, method step 2004 includes method step 2100.Method step 2100 shows that, in one implementation, transmitting themessage to at least one of the at least two desired recipients caninclude, but is not limited to, performing device processing wherein atleast one device address of the at least two desired recipients ischecked for valid format. (For example, such as was at least partiallydescribed in the herein incorporated by reference Provisional PatentApplication No. 60/282,381.) The remaining method steps of FIG. 21function substantially as described elsewhere herein.

With reference now to FIG. 22, shown is an implementation of thehigh-level logic flowchart shown in FIG. 20. Depicted in FIG. 22 isthat, in one implementation, method step 2004 includes method step 2200.Method step 2200 shows that, in one implementation, transmitting themessage to at least one of the at least two desired recipients caninclude, but is not limited to, performing device provisioning whereinat least one phone number of the at least two desired recipients isdetermined as either active or inactive. (For example, such as was atleast partially described in the herein incorporated by referenceProvisional Patent Application No. 60/282,381.) The remaining methodsteps of FIG. 22 function substantially as described elsewhere herein.

With reference now to FIG. 23, shown is an implementation of thehigh-level logic flowchart shown in FIG. 20. Depicted in FIG. 23 isthat, in one implementation, method step 2004—transmitting the messageto at least one of the at least two desired recipients—can include, butis not limited to, method steps 2300-2306. Method step 2300 showsperforming device detection whereby a specific device capability isassociated with at least one of the at least two desired recipients.Method step 2302 shows retrieving at least onedevice-capability-specific file set appropriate to the specific devicecapability. Method step 2304 shows formulating the message into adevice-capability-specific message via use of the at least onedevice-capability-specific file set. Method step 2306 shows transmittingthe device-capability-specific message to the at least one wirelessdevice. (For example, such as was at least partially described in theherein incorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 23 functionsubstantially as described elsewhere herein.

With reference now to FIG. 24, shown is an implementation of thehigh-level logic flowchart shown in FIG. 23. Depicted in FIG. 24 isthat, in one implementation, method step 2300 can include method step2400. Illustrated is that, in one implementation, performing devicedetection whereby a specific device capability is associated with atleast one of the at least two desired recipients can include, but is notlimited to, detecting a device capability associated with the at leastone of the at least two desired recipients. (For example, such as was atleast partially described in the herein incorporated by referenceProvisional Patent Application No. 60/282,381.) The remaining methodsteps of FIG. 24 function substantially as described elsewhere herein.

With reference now to FIG. 25, shown is an implementation of thehigh-level logic flowchart shown in FIG. 24. Depicted in FIG. 25 isthat, in one implementation, method step 2400 can include method step2500. Illustrated is that, in one implementation, detecting a devicecapability associated with the at least one of the at least two desiredrecipients can include, but is not limited to, detecting the devicecapability to be one of a device-capability group which includes a WML(Wireless Markup Language) capable browser, a CHTML (Compact HypertextMarkup Language) capable browser, a Pocket IE (Internet Explorer) HTML(Hypertext Markup Language) capable browser, and a voice XML (ExtensibleMarkup Language) capable browser. (For example, such as was at leastpartially described in the herein incorporated by reference ProvisionalPatent Application No. 60/282,381.) The remaining method steps of FIG.25 function substantially as described elsewhere herein.

With reference now to FIG. 34, shown is an implementation of thehigh-level logic flowchart shown in FIG. 24. Depicted in FIG. 34 isthat, in one implementation, method step 2400 can include method step3400. Illustrated is that, in one implementation, detecting a devicecapability associated with the at least one of the at least two desiredrecipients can include, but is not limited to, detecting a commerciallyavailable browser. In one device implementation, method step 3400 isachieved by a wireless web server entity (e.g., a part of MMP engine 104of FIG. 1) when a user (e.g., a member of group of desired recipients100) contacts the wireless web server entity via a wireless web browseron the users web-enabled cell phone (e.g., wireless device 108).

For additional examples of the process of FIG. 34 and deviceimplementations thereof, please see herein incorporated by referenceProvisional Patent Application No. 60/282,381. The remaining methodsteps of FIG. 34 function substantially as described elsewhere herein.

With reference now to FIG. 35, shown are two alternate implementationsof the high-level logic flowchart shown in FIG. 34. Depicted in FIG. 35is that, in one implementation, method step 3400 includes method step3500; further depicted is that, in another implementation, method step3400 includes method step 3502; further depicted is that, in yet anotherimplementation, method step 3400 includes method step 3504. Method step3500 shows that, in one implementation, detecting a commerciallyavailable browser can include, but is not limited to, associating amark-up language with a detected Pocket IE browser. In one deviceimplementation, method step 3500 is achieved by a wireless web serverentity (e.g., a part of MMP engine 104 of FIG. 1) via recall of amark-up language type associated with a version number of Pocket IEbrowser when a user (e.g., a member of group of desired recipients 100)contacts the wireless web server entity via a wireless web browser onthe users web-enabled cell phone (e.g., wireless device 108).

Method step 3502 shows that, in one implementation, detecting acommercially available browser can include, but is not limited to,associating a mark-up language with a detected UP.browser. In one deviceimplementation, method step 3502 is achieved by a wireless web serverentity (e.g., a part of MMP engine 104 of FIG. 1) via recall of amark-up language type associated with a version number of UP.browserwhen a user (e.g., a member of group of desired recipients 100) contactsthe wireless web server entity via a wireless web browser on the usersweb-enabled cell phone (e.g., wireless device 108).

Method step 3504 shows that, in one implementation, detecting acommercially available browser can include, but is not limited to,associating a mark-up language with a detected Palm Query Applicationbrowser. In one device implementation, method step 3504 is achieved by awireless web server entity (e.g., a part of MMP engine 104 of FIG. 1)via recall of a mark-up language type associated with a version numberof Palm Query Application browser when a user (e.g., a member of groupof desired recipients 100) contacts the wireless web server entity via awireless web browser on the users web-enabled cell phone (e.g., wirelessdevice 108).

For additional examples of the process of FIG. 35 and deviceimplementations thereof, please see herein incorporated by referenceProvisional Patent Application No. 60/282,381. The remaining methodsteps of FIG. 35 function substantially as described elsewhere herein.

With reference now to FIG. 26, shown is an implementation of thehigh-level logic flowchart shown in FIG. 24. Depicted in FIG. 26 isthat, in one implementation, method step 2400 can include method step2600. Illustrated is that, in one implementation, detecting a devicecapability associated with the at least one of the at least two desiredrecipients can include, but is not limited to, detecting the devicecapability via scanning of a Hyper Text Transfer Protocol (http) header.(For example, such as was at least partially described in the hereinincorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 26 functionsubstantially as described elsewhere herein.

With reference now to FIG. 27, shown is an implementation of thehigh-level logic flowchart shown in FIG. 23. Depicted in FIG. 27 isthat, in one implementation, method step 2302 can include method step2700. Illustrated is that, in one implementation, retrieving at leastone device-capability-specific file set appropriate to the specificdevice capability can include, but is not limited to, retrieving atleast one device-capability-specific XSL (Extensible Style Language)file set from a device-capability-specific XSL-file-set group whichincludes a WML capability-specific XSL file set, a CHTMLcapability-specific XSL file set, a Pocket IE HTML capability-specificXSL file set, and a voice XML capability-specific XSL file set. (Forexample, such as was at least partially described in the hereinincorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 27 functionsubstantially as described elsewhere herein.

With reference now to FIG. 28, shown is an implementation of thehigh-level logic flowchart shown in FIG. 23. Depicted in FIG. 28 isthat, in one implementation, method step 2304 can include method step2800. Illustrated is that, in one implementation, formulating themessage into a device-capability-specific message via use of the atleast one device-capability-specific file set can include, but is notlimited to, utilizing the at least one device-capability-specific fileset in conjunction with an XML representation of the message to create amessage appropriate to a browser wherein the browser is selected from abrowser-capability group which includes a WML capable browser, a CHTMLcapable browser, a Pocket IE HTML capable browser, and a voice XMLcapable browser. (For example, such as was at least partially describedin the herein incorporated by reference Provisional Patent ApplicationNo. 60/282,381.) The remaining method steps of FIG. 28 functionsubstantially as described elsewhere herein.

With reference now to FIG. 29, shown is an implementation of thehigh-level logic flowchart shown in FIG. 20. Depicted in FIG. 29 isthat, in one implementation, method step 2004 includes method step 2900.Method step 2900 shows that, in one implementation, transmitting themessage to at least one of the at least two desired recipients caninclude, but is not limited to, sending the message to at least one ofthe at least two desired recipients via a wireless link. (For example,such as was at least partially described in the herein incorporated byreference Provisional Patent Application No. 60/282,381.) The remainingmethod steps of FIG. 29 function substantially as described elsewhereherein.

With reference now to FIG. 30, shown is an implementation of thehigh-level logic flowchart shown in FIG. 20. Depicted in FIG. 30 isthat, in one implementation, method step 2004 includes method step 3000.Method step 3000 shows that, in one implementation, transmitting themessage to at least one of the at least two desired recipients caninclude, but is not limited to, repetitively attempting to send themessage to each of the at least two desired recipients. (For example,such as was at least partially described in the herein incorporated byreference Provisional Patent Application No. 60/282,381.) The remainingmethod steps of FIG. 30 function substantially as described elsewhereherein.

With reference now to FIG. 31, shown is an implementation of thehigh-level logic flowchart shown in FIG. 20. Depicted in FIG. 31 isthat, in one implementation, method step 2002 includes method step 3100.Method step 3100 shows that, in one implementation, receiving inputrequesting response aggregation drawn upon a message having at least twodesired recipients can include, but is not limited to, receiving inputdefining the message to have at least one message-structure itemselected from a message-structure group including a subject; a responseoption; an associated ability to allow at least one desired recipient tosee at least one other of the at least two desired recipients; a messagebody; at least one yes-no-type answer question; at least onenumeric-response-type answer question; at least onetextual-response-type answer question; at least onemultiple-choice-response-type answer question; at least one meeting datewhich can include either or both a day and a time; at least one meetinglocation; or at least one meeting RSVP request; at least one eventdescriptor wherein the event descriptor can include, but is not limitedto, a party, a breakfast, a lunch, a dinner, a movie, a game, a concert,or a miscellaneous occurrence; at least one event location; and at leastone event RSVP request. (For example, such as was at least partiallydescribed in the herein incorporated by reference Provisional PatentApplication No. 60/282,381.) The remaining method steps of FIG. 31function substantially as described elsewhere herein.

With reference now to FIG. 32, shown is an implementation of thehigh-level logic flowchart shown in FIG. 20. Depicted in FIG. 32 isthat, in one implementation, method step 2002 includes method step 3200.Method step 3200 shows that, in one implementation, receiving input caninclude, but is not limited to, receiving input from an entity selectedfrom an entity group including an alphanumeric processing entity and avoice-processing entity. For example, in one implementation method step3200 is achieved via a wireless device (e.g., wireless device 102)transmitting to a computational entity (e.g., a part of MMP engine 104of FIG. 1) which understands and accepts voice input, and whichthereafter processes the voice input and reformulates it intoalphanumeric input and subsequently transmits the alphanumeric input tothe wireless web server entity (e.g., a part of MMP engine 104 ofFIG. 1) which understands and accepts alphanumeric input. In anotherimplementation. In one device implementation, method step 3200 isachieved via a wireless device (e.g., wireless device 102) transmittingto a wireless web server entity (e.g., a part of MMP engine 104 ofFIG. 1) that understands and accepts alphanumeric input.

(For example, such as was at least partially described in the hereinincorporated by reference Provisional Patent Application No.60/282,381.) The remaining method steps of FIG. 32 functionsubstantially as described elsewhere herein.

IV. General Implementation Issues Related to Processes and/or SystemsDescribed Herein

Those having ordinary skill in the art will recognize that the state ofthe art has progressed to the point where there is little distinctionleft between hardware and software implementations of aspects ofsystems; the use of hardware or software is generally (but not always,in that in certain contexts the choice between hardware and software canbecome significant) a design choice representing cost vs. efficiencytradeoffs. Those having ordinary skill in the art will appreciate thatthere are various vehicles by which processes and/or systems describedherein can be effected (e.g., hardware, software, and/or firmware), andthat the preferred vehicle will vary with the context in which theprocesses are deployed. For example, if an implementer determines thatspeed and accuracy are paramount, the implementer may opt for a hardwareand/or firmware vehicle; alternatively, if flexibility is paramount, theimplementer may opt for a solely software implementation; or, yet againalternatively, the implementer may opt for some combination of hardware,software, and/or firmware. Hence, there are several possible vehicles bywhich the processes described herein may be effected, none of which isinherently superior to the other in that any vehicle to be utilized is achoice dependent upon the context in which the vehicle will be deployedand the specific concerns (e.g., speed, flexibility, or predictability)of the implementer, any of which may vary.

The foregoing detailed description has set forth various embodiments ofthe devices and/or processes via the use of block diagrams, flowcharts,and examples. Insofar as such block diagrams, flowcharts, and examplescontain one or more functions and/or operations, it will be understoodas notorious by those within the art that each function and/or operationwithin such block diagrams, flowcharts, or examples can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or any combination thereof. In one embodiment, the presentinvention may be implemented via Application Specific IntegratedCircuits (ASICs). However, those skilled in the art will recognize thatthe embodiments disclosed herein, in whole or in part, can beequivalently implemented in standard Integrated Circuits, as one or morecomputer programs running on one or more computers (e.g., as one or moreserver programs running on one or more computer systems), as one or moreprograms running on one or more processors (e.g., as one or more thinclient programs running on one or more processors), as firmware, or asvirtually any combination thereof, and that designing the circuitryand/or writing the code for the software or firmware would be wellwithin the skill of one of ordinary skill in the art in light of thisdisclosure. In addition, those skilled in the art will appreciate thatthe mechanisms of the present invention are capable of being distributedas a program product in a variety of forms, and that an illustrativeembodiment of the present invention applies equally regardless of theparticular type of signal bearing media used to actually carry out thedistribution. Examples of a signal bearing media include, but are notlimited to, the following: recordable type media such as floppy disks,hard disk drives, CD ROMs, digital tape, and transmission type mediasuch as digital and analogue communication links using TDM or IP basedcommunication links (e.g., packet links).

In a general sense, those skilled in the art will recognize that thevarious embodiments described herein which can be implemented,individually and/or collectively, by a wide range of hardware, software,firmware, or any combination thereof can be viewed as being composed ofvarious types of “electrical circuitry.” Consequently, as used herein“electrical circuitry” includes, but is not limited to, electricalcircuitry having at least one discrete electrical circuit, electricalcircuitry having at least one integrated circuit, electrical circuitryhaving at least one application specific integrated circuit, electricalcircuitry forming a general purpose computing device configurable by acomputer program (e.g., a general purpose computer configurable by acomputer program or a microprocessor configurable by a computerprogram), electrical circuitry forming a memory device (e.g., any andall forms of random access memory), and electrical circuitry forming acommunications device (e.g., a modem, communications switch, oroptical-electrical equipment).

Those skilled in the art will recognize that it is common within the artto describe devices and/or processes in the fashion set forth herein,and thereafter use standard engineering practices to integrate suchdescribed devices and/or processes into data processing systems. Thatis, the devices and/or processes described herein can be integrated intoa data processing system via a reasonable amount of experimentation.FIG. 33 shows an example representation of a data processing system intowhich at least a part of the herein described devices and/or processesmay be integrated with a reasonable amount of experimentation.

With reference now to FIG. 33, depicted is a pictorial representation ofa conventional data processing system in which illustrative embodimentsof the devices and/or processes described herein may be implemented. Itshould be noted that a graphical user interface systems (e.g., MicrosoftWindows 98 or Microsoft Windows NT operating systems) and methods can beutilized with the data processing system depicted in FIG. 33. Dataprocessing system 3320 is depicted which includes system unit housing3322, video display device 3324, keyboard 3326, mouse 3328, andmicrophone (not shown). Data processing system 3320 may be implementedutilizing any suitable computer such as a DELL portable computer system,a product of Dell Computer Corporation, located in Round Rock, Tex.;Dell is a trademark of Dell Computer Corporation.

The foregoing described embodiments depict different componentscontained within, or connected with, different other components. It isto be understood that such depicted architectures are merely exemplary,and that in fact many other architectures can be implemented whichachieve the same functionality. In a conceptual sense, any arrangementof components to achieve the same functionality is effectively“associated” such that the desired functionality is achieved. Hence, anytwo components herein combined to achieve a particular functionality canbe seen as “associated with” each other such that the desiredfunctionality is achieved, irrespective of architectures or intermedialcomponents. Likewise, any two components so associated can also beviewed as being “operably connected”, or “operably coupled”, to eachother to achieve the desired functionality.

While particular embodiments of the present invention have been shownand described, it will be obvious to those skilled in the art that,based upon the teachings herein, changes and modifications may be madewithout departing from this invention and its broader aspects and,therefore, the appended claims are to encompass within their scope allsuch changes and modifications as are within the true spirit and scopeof this invention. Furthermore, it is to be understood that theinvention is solely defined by the appended claims. It will beunderstood by those within the art that, in general, terms used herein,and especially in the appended claims (e.g., bodies of the appendedclaims) are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be also understood by those within the art that if aspecific number of an introduced claim element is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimelements. However, the use of such phrases should not be construed toimply that the introduction of a claim element by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim element to inventions containing only one such element,even when the same claim includes the introductory phrases “one or more”or “at least one” and indefinite articles such as “a” or “an”; the sameholds true for the use of definite articles used to introduce claimelements. In addition, even if a specific number of an introduced claimelement is explicitly recited, those skilled in the art will recognizethat such recitation should typically be interpreted to mean at leastthe recited number (e.g., the bare recitation of “two elements,” withoutother modifiers, typically means at least two elements, or two or moreelements).

1.-20. (canceled)
 21. A method comprising: displaying a plurality of categories, wherein a first category comprises a number of recipients of a managed message that have indicated that they will attend an event to which the managed message relates, the managed message representing a message including an event invitation transmitted to a plurality of desired recipients; displaying a first list of e-mail addresses of recipients from the number of recipients in response to a selection of the first category; displaying, in response to a selection of a first selected recipient of the first list of e-mail addresses of recipients, a name of the first selected recipient, a date the managed message was sent to the first selected recipient, and a date the managed message was viewed by the first selected recipient; and displaying an RSVP by the first selected recipient, including comments from the first selected recipient.
 22. The method of claim 21, further comprising: displaying a recipient response summary, wherein the recipient response summary indicates a total number of the recipients of the managed message and a total number of the recipients of the managed message that have indicated that they will attend the event to which the managed message relates.
 23. The method of claim 22, wherein displaying the recipient response summary comprises: displaying a total number of recipients that have viewed the managed message, a total number of recipients that have not viewed the managed message, and a total number of recipients for whom the managed message is undeliverable.
 24. The method of claim 21, wherein displaying the plurality of categories comprises: displaying a second category, the second category comprising a number of recipients of the managed message that have viewed the managed message.
 25. The method of claim 24, further comprising: in response to selection of the second category, displaying a second list of e-mail addresses of recipients from the number of recipients of the managed message that have viewed the managed message.
 26. The method of claim 25, further comprising: displaying, in response to a selection of a second selected recipient of the second list of e-mail addresses of recipients, a name of the second selected recipient, a date the managed message was sent to the second selected recipient, and a date the managed message was viewed by the second selected recipient.
 27. The method of claim 24, wherein displaying the plurality of categories further comprises: displaying a third category, the third category comprising a number of recipients that have not viewed the managed message.
 28. The method of claim 27, further comprising: in response to selection of the third category, displaying a third list of e-mail addresses of recipients from the number of recipients number of recipients that have not viewed the managed message.
 29. The method of claim 28, further comprising: displaying, in response to a selection of a third selected recipient of the third list of e-mail addresses of recipients, a name of the third selected recipient and a date the managed message was sent to the third selected recipient.
 30. A system comprising: means for displaying, on a display screen of a wireless device, a plurality of categories, wherein a first category comprises a number of recipients of a managed message that have indicated that they will attend an event to which the managed message relates, the managed message representing a message including an event invitation transmitted to a plurality of desired recipients; means for displaying a first list of e-mail addresses of recipients from the number of recipients in response to a selection of the first category; means for displaying, in response to a selection of a first selected recipient of the first list of e-mail addresses of recipients, a name of the first selected recipient, a date the managed message was sent to the first selected recipient, and a date the managed message was viewed by the first selected recipient; and means for displaying an RSVP by the first selected recipient, including comments from the first selected recipient.
 31. The system of claim 30, further comprising: means for displaying a recipient response summary, wherein the recipient response summary indicates a total number of the recipients of the managed message and a total number of the recipients of the managed message that have indicated that they will attend the event to which the managed message relates
 32. The system of claim 31, wherein the means for displaying the recipient response summary comprises: means for displaying a total number of recipients that have viewed the managed message, a total number of recipients that have not viewed the managed message, and a total number of recipients for whom the managed message is undeliverable.
 33. The system of claim 30, wherein the means for displaying the plurality of categories comprises: means for displaying a second category, the second category comprising a number of recipients of the managed message that have viewed the managed message.
 34. The system of claim 33, further comprising: means for displaying, in response to selection of the second category, a second list of e-mail addresses of recipients from the number of recipients number of recipients of the managed message that have viewed the managed message.
 35. The system of claim 34, further comprising: means for displaying, in response to a selection of a second selected recipient of the second list of e-mail addresses of recipients, a name of the second selected recipient, a date the managed message was sent to the second selected recipient, and a date the managed message was viewed by the second selected recipient.
 36. The system of claim 33, wherein the means for displaying the plurality of categories further comprises: means for displaying a third category, the third category comprising a number of recipients that have not viewed the managed message.
 37. The system of claim 36, further comprising: means for displaying, in response to selection of the third category, a third list of e-mail addresses of recipients from the number of recipients number of recipients that have not viewed the managed message.
 38. The system of claim 37, further comprising: means displaying, in response to a selection of a third selected recipient of the third list of e-mail addresses of recipients, a name of the third selected recipient and a date the managed message was sent to the third selected recipient.
 39. A tangible computer readable medium having instructions stored thereon, the instructions comprising: instructions for displaying, on a display screen of a wireless device, a plurality of categories, wherein a first category comprises a number of recipients of a managed message that have indicated that they will attend an event to which the managed message relates, the managed message representing a message including an event invitation transmitted to a plurality of desired recipients; instructions for displaying a first list of e-mail addresses of recipients from the number of recipients in response to a selection of the first category; instructions for displaying, in response to a selection of a first selected recipient of the first list of e-mail addresses of recipients, a name of the first selected recipient, a date the managed message was sent to the first selected recipient, and a date the managed message was viewed by the first selected recipient; and instructions for displaying an RSVP by the first selected recipient, including comments from the first selected recipient.
 40. The system as in claim 39, further comprising: instructions for displaying a recipient response summary, wherein the recipient response summary indicates a total number of the recipients of the managed message and a total number of the recipients of the managed message that have indicated that they will attend the event to which the managed message relates, a total number of recipients that have viewed the managed message, a total number of recipients that have not viewed the managed message, and a total number of recipients for whom the managed message is undeliverable. 